Step 3 Creating a New Environment

Environment Management in Rules Workbench

Environment management in Oracle Insurance Rules Workbench provides a secure and consistent framework for creating, organizing, and maintaining environments across the application lifecycle. Each environment is configured with connections to a Palette database and an Internal Versioning System (IVS) database. Tracks are used within IVS to group related environments that share a common ruleset lineage, enabling controlled promotion and migration of rules across stages such as development, testing, and production.

Environment setup and management functions are available only to the user assigned the Build Manager role, ensuring appropriate access controls are maintained.

The Release Management Entry flag determines the environment role:

  • Toggle Enabled (True) : Designates the environment as a Source, responsible for rule creation and maintenance. A source environment can migrate rules to multiple target environments within the same track.

  • Toggle disabled (False) : Designates the environment as a Target, which receives rules migrated from the designated source.

To maintain clear rule ownership and lineage, only one source environment is permitted per track.

Rules Workbench maintains backward compatibility with existing IVS implementations and established workflows and integrations from Oracle Insurance Rules Palette-based designs. Environments can be safely deleted when no longer required. The deletion process removes all user mappings within the Oracle Insurance Rules Workbench schema, while IVS configuration records remain intact.

First User (Security Manager) Creation

A First User—referred to as the Security Manager—must be specified during initial or new environment creation. This assignment is mandatory:

  • If the Security Manager is not defined, the environment creation process is automatically interrupted.

  • The Security Manager account is mapped to the environment schema and registered in the IVS user table.

  • The Security Manager serves as the primary contact for assigning security roles and privileges to other IVS users within the environment.

Prerequisites

  • An active user account assigned the Build Manager role.

  • Required database schemas (Palette and IVS, and connection details) are prepared and available.

  • Rules Workbench application accessible from the designated URL.

Access and Page Layout

  • Log in to Oracle Insurance Rules Workbench using a user account with Build Manager role.

  • The Environments configuration screen is displayed, consisting of

    • Environment Panel (Left): List of environments and a “+” icon for adding a new environment.

    • Details Panel (Right): Editable sections for defining environment details and viewing attributes of selected environments.

Steps to Create a New Environment

Method -1 : Manual Creation

  1. In the Environment panel, select the “+” icon to add a new environment. A row labeled New Environment appears in the list.

  2. In the Configuration panel, complete the following sections:

    1. Details

      1. Name: Enter a unique environment name (Required).

    2. Palette

      1. Database Platform: Select the database platform from the drop-down list.

      2. Database Url: Enter the database connection URL.

      3. Database User Name: Enter the database username.

      4. Database Password: Enter the database password.

      5. NBU and Products: Enable toggles as needed.

      6. IVS: Enable this toggle to configure Internal Versioning System (IVS) settings.

        • Enabling this toggle displays the IVS Configuration section..

    3. Internal Versioning System (IVS) - This section appears only if the IVS toggle is enabled.

      1. Release Management: Enable for structured release management.

      2. Release Management Entry Environment: Enable if this environment will serve as the Source Environment for its track.

      3. Database Platform: Choose the IVS database platform (SQL Server, Oracle, or DB2).

      4. Database Url: Enter the IVS database connection URL.

      5. Database User Name: Enter the IVS database username.

      6. Database Password: Enter the IVS database password.

      7. IVS Environment: Enter the identifier for the IVS environment.

      8. IVS Track Number: Enter the track number associated with the environment.

      9. Deployment Sequence: Specify the deployment sequence within the track.

        Note: The combination of IVS Environment, IVS Track Number,Deployment Sequence must be unique for each environment.

      10. Reuse Environment, Track & Sequence - Turn on this toggle to reuse existing IVS configurations instead of creating a new track and sequence.

        Note: If this toggle is not activated and an existing track and sequence are selected, a validation error occurs indicating that the 'Track and Sequence combination with these values already exists.'

      11. Create First User : Enable this toggle to create the First User (Security Manager) for the environment.

        • Mandatory for initial environment creation.

        • When enabled, provide the following details:

          • Security Role Name

            • A role named “security manager” is created alongside the first user during environment setup.

            • Auto-filled using the format SecurityManager(Prefix)+ IVS Environment + IVS Track Number (e.g., SecurityManagerDemo1).

        • First User Name: Enter the Security Manager username. This is also the first IVS username.

        • Password and Confirm Password: Provide and confirm the Security Manager password.

  3. After completing all configuration sections, click Create to save and register the new environment.

 

Method 2: Duplicate Existing Environment

An Alternate Approach: Duplicating an Existing Environment

  1. In the Environments Panel, click the “…” icon beside an existing environment.

  2. Click Duplicate.

  3. A new environment with the suffix “- Copy” appears.

  4. Update all mandatory details such as Name, Database Configuration, and IVS fields.

  5. Click Create to save.

System Behavior

  • If a required field is empty, the system displays “Enter a value” below the field.

  • If the First User information is omitted when required, the system displays “First user creation is required for the environment.”

  • Once successfully created, the environment appears in the Environments panel (left panel).

Post-Environment Creation Steps

After environment creation, configuration and user-mapping options are available in the Details panel.

Important: After environment creation, Palette and IVS database connection configuration values are read-only in Rules Workbench. A new environment must be created to change these values.

Available options in the Configuration Panel

  1. Import Users - Select Import Users to bulk-import existing users into the environment.

    1. During the import process, username and email are the same as the username in the IVS/non-IVS environment, while the password remains unchanged. If the ‘configurer’ role does not already exist, it is created and assigned the 'Manage Rules & Dashboard' privilege. All imported users are granted the ‘configurer’ role. If a user with the specified username already exists in the Rules Workbench schema, the user’s email address and password are not updated; however, the user is granted the ‘configurer’ role.

  2. Delete - Allows current Environment deletion.

    1. Select Delete to permanently remove the environment from Rules Workbench.

    2. Deletion removes user mappings within the Oracle Insurance Rules Workbench schema; IVS configuration records remain intact.

User Mapping (Collapsible Section)

This collapsible section Manage user-to-environment mappings.

Pre-requisite

  • Ensure the user exists on the Users screen with an assigned role before mapping to the environment. Mapping cannot proceed unless both conditions are met.

Steps to Map a New User

  1. Scroll down to User Mapping section and click expand icon.

  2. Click Add new button.

  3. In the new row, enter the User Name and the corresponding Environment User Name.

    1. User Name refers to the Rules Workbench username.

    2. Environment User Name refers to the existing username in the IVS or non-IVS environment.

  4. Select the ✓ icon in the Action column to save the row, or select X to discard.

  5. Click Update button to apply the changes.

  6. Click Cancel to exit without saving changes.

Remove existing user mapping

  1. Locate the user to be unmapped in the User Mapping grid.

  2. Select the checkbox in the Delete column for the selected user.

  3. Click the Update button to confirm and apply the removal.

Note: Log out of the Build Manager account. Then, log in to the new environment using the Security Manager account to configure security roles and complete environment-specific setup.